home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Diamond Collection
/
The Diamond Collection (Software Vault)(Digital Impact).ISO
/
cdr37
/
tunlgnb4.zip
/
TUNLGON.NFO
< prev
next >
Wrap
Text File
|
1995-03-27
|
28KB
|
602 lines
------------------------------------------------------------------------------
▀█▀ █▄▌▐▀█ FORUMHACK LOGON PPE Version 1.9d Development Build #4
* This is NOT a full public release. It is for development, concept, and
system testing purposes only. It is assumed established PCB SysOps will
evaluate this PPE, and we value your input during our final stages of
development in the PPE to offer a better replacement then others used
to this day.
* Numerous changes/improvements and added support files in this build. Please
take the time to read the SETUP DETAIL docs to insure less suffering on your
part :)
PPE Codeing/Testing by BayBeVet for the TUNWarez Programming Team 1994-95
EXE Coding/Testing by BayBeVet for the TUNWarez Programming Team 1994-95
PPE Testing by The Chairman for the TUNWarez Programming Team 1994-95
PPE Code/Rights Reserved 1994-95 by The TUNWarez Programing Team
Support BBS: The Underground Network (516)281-8139 28.8 V.34 Node 1 of 5
------------------------------------------------------------------------------
HISTORY:
--------
This PPE grew from a need at our board. After many years of running our
BBS under various software packages, we liked the basic forum based logon
process. While there were some Forum-Hack logon PPE's available when we made
our switch to PCBoard, the realistic concern of possible back doors rules them
out. In addition, none were totally complete, often requiring an additional
PPE to support features like Infoforms or New User Voting. The result was the
birth of this PPE to offer a better choice then nearly all the presently
available forum style logon PPE's for PCBoard.
FEATURES
--------
-> Unlike many other popular PPE's in use out there, this one has no damn
"Backdoors" in it ! We are too old to be brothered with that stuff.
The TUNPPE you downloaded from our board is the same damn one, code for
code, that we use on our board, so think about it :)
-> Fully Multi-Node ready Welcome Screen Randomizer. Welcome screens are
text based ASCII/ANSi Screens, which may contain if desired ANSi Codes,
PCB color, and PCB macro codes. A screen is choosen at logon at random and
presented to the user. Unlike other logon PPE's, the total number of
screens you may have to be choosen at random is limited only by the total
number of files you can place into a Sub-Directory. It may be any valid
DOS filename as well, as it is NOT extension based.
-> Like the Welcome Screens Above, Fully randomized User/System Stats Screens
are fully supported. Again, unlimited amounts, fully randomized at logon
-> Two Forum-Style InfoForm questionaires, SysOp Information and one used for
the New User Voting Booth. Both Infoforms are 100% SysOp Configurable via
standard ANSi screens and .CFG text files to create that custom look for
your board, or develop infoforms that meet your needs. Infoforms are 100%
Mandatory when new user logon to your board. An option is available to hang
up on new users after completeing the required infoforms.
* This works fully hand in hand with the New User Voting Feature *
* Below to Give You A Fully Functional, Nearly Care Free NUV Process. *
-> Fully Multi-node Able, Non-Mandatory, New User Voting Booth. Together with
the Infoforms above, you have all you need for a successful NUV. Unlike
other NUV's, the logic of this NUV allows for a NON-MANDATORY NUV. In
otherwords, users are not forced to vote on logon if they choose not to.
This allows the user to vote when logging on later, should the same new user
still be present in the NUV. Fully record keeping of of NUV voting records
are supported, providing the SysOp with a log of Who voted on which user,
what the users vote was, any user comments, and who cased the deciding vote.
SysOp commands at the NUV include Auto-Validating, Auto-deleteing as well
as viewing Infoform #1, the SysOp ( private ) Infoform. Total SysOp
configurablility of security level to vote, number of votes (yes/no),
Default Validated User Level ( NUV Validated User ) and SysOp Comment One
Note, level to use SysOp commands (SysOp Infoform/Autovalidate/AutoDelete)
Support should be possible for up to 4 billion total infoform/nuv records
according to Mr.Clark, so a mortal SysOp should do fine.
-> Forum Style 1-liners feature allows users to leave 1 line comments ( or in
most cases BBS ads ) to future users that logon to your system. Total
number of permitted 1 liners is configurable by the SysOp.
-> Lastcallers Display. This displays the Date/Time, UserName, the SysOp
Comment Number 1 ( instead of location ), Users connect Baudrate, and the
Node number. Each of these fields are 100% fully color configurable so you
may custom its colors to match your boards. Local Calls May Also Be Toggled
Hidden or Not in Last Callers ( Hide the sysop logons ). The total number
of last callers tracked is also 100% SysOp configurable.
-> User-Wide System News Displays SysOp Made Text/ANSi Files to users during
the logon process. Reading is mandatory. Only files dated after the users
last call date are presented. Just place the files into the directory and
bingo, they are installed into the logon process.
-> Turbo Logon. SysOp configurable to toggle on/off. Allow users to bypass
much of the logon process. Mandatory parts of the logon process are
the welcome screen, the turbo logon prompt, and system news. ( oh, and how
course Infoforms for new users )
-> Suggested Uploads Display/SysOp Commands Option. We use this screen to
display a list of suggested upload to users. Another popular usage of this
screen is allowing SysOps the ability to call other logon type PPE's, such
as top UL/DL'ers, message from last user, and that sort. This allows those
PPE's to be intergrated into the overall logon process, and may be over
passed by user via Turbo-Logon feature of TUNLogon. Note, these PPE's would
be called by the standard ! command used by PCBoard in text files.
-> Nearly All Display Screens and Prompts are 100% SysOp Configurable using
in most cases standard ANSI/Text screens ( PCB @Color Codes are valid ), to
create that custom look ( no more of that damn name of the PPE author on
each and every screen and part of the PPE hard coded in! ). Furthermore,
some prompts may even be replaced either with future TUNLogonPPE Enhancement
Modules or 3rd party PPE's ( for lightbar YES/NO Prompts for example, either
your own or other compatible available PPE's ). This allows your board to
be unique instead of looking like everyone else's board ( Like SysOp's that
use SLogon/Provote for example, all their boards look nearly the same during
the logon process )
-> Install Utility ( TUNSTALL ) makes installation onto your harddrive and your
PCB Board setup a breeze. You may have the install utility modify the needed
PCBTEXT records and create the needed files, or you may choose during the
install NOT to do so and instead follow the manual instructions provided
below.
-> Configuration Utility ( TUNCFG.EXE ) makes configuration changes easy
( Not Provided in this Beta Test Release )
-> TUN'EM ( TUN "Engine/Module" ) program design allows for future
compatiablity with other TUNPPE's as well as the possiblility of enhancement
modules which may be used to customize/change certain parts of the PPE
should they become available in the future. ( For example, a module may be
changed for a different last callers screen format, different one-liners
interface, or perhaps for an infoform module to support more then 2
infoforms if warranted ).
-> The Logon process is as follows:>Infoforms
>Welcome Screen(s)
>Turbo-Logon Prompt ( If ON )
--- If Turbo Logon Answer Is NO Then --
>Last Callers
>User/System Stat Screen(s)
>One Liners
>NUV
>Suggested UL's/SysOp Options
----- End Turbo Logon Process ----
>System News
INSTALLATION
------------
1) Unzip contents of ZIP to a work directory
2) run TUNSTALL.EXE
or for Manual Installations
----------------------------
Installation is similar to many popular PPE's in use today, But here is
a down n dirty installation process
1) Create any directory you wish, and copy all program files into there.
Of course multinode users should make sure this area is accessable by
all the nodes, yes :)
2) Place a call to the PPE anywhere you wish in your logon process. We
suggest the following.
a) Run PCBSETUP for each node. Select G, Then Select D, under options
locate "SCAN FOR NEW BULLETINS", Set this to "YES". Save and exit
b) Create a textfile called BULLETIN.TXT with the following line
!c:\pcb\ppe\tunlogon\tunlgon.ppe
Of course, if you all ready use a bulletin file, edit it as warranted and
change the drive/path shown above to match where you are installing the
TUNLGON.PPE ( helps I suppose heh :) )
c) Run MKPCBTXT, goto record 665, and edit it as follows
%c:\pcb\gen\bulletin.txt
Change Drive/Path listed above to match location you placed it of course
3) Edit the TUNLGON.CFG as warranted to meet your needs. Descriptions of each
line are listed in that file. Read it carefully!
an .EXE file will be used to edit this file to streamline the process.
4) Verify in your PCBSETUP that your WORK path is FULLY defined with a DRIVE
and A PATH, not just a ".." or a "/". It must be defined !
5) Verify in your PCBSETUP that level for users that refuse to register is
0 and users that agree to register is 1
Thats it. Logon now, and it should work NO problem..
**** For SysOps that are Updating Older 1.9d Builds
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It is recommended that you install this build to another directory
independent from any other installed versions. Do a FULL installation, and
then overwrite any screens you may of customized ( \DISPLAY\*.* ), plus the
full contents of the following directorys and files
\DATA\*.*
\NUV\*.*
\INFOFORM\*.*
tunlgon.cfg
This will preserve your present New Users, 1 Liners, Last Callers,
and All related infoforms/answers/ and NUV records as well as your current
configuration. Make sure to take the time to read the docs below
==============================================================================
------------------------------------------------------------------------------
Setup Detail Docs
----------------------
Prompts
--------
User Input Prompt Color is definable in the TUNLGON.CFG file. It uses
standard PCB @X color codes. In addition, many prompts thru out the PPE are
custom configurable via files listed in the \DISPLAY directory.
Filename(s): Turbo.pmt
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user if he
she wishes to use the TURBO LOGON feature.
Filename(s): prompt.wel
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user to hit
any key to continue. Customize this file as warranted for your boards needs
and the look your desire. Standard PCB @X Color Codes are valid as well.
* See other sections below for additional prompts related to *
* other parts of the PPE as listed below *
Infoforms
-----------
Infoforms used by TUNLogonPPE are similar to those used in the past by
forum hacks, meaning the use standard ANSi files. With this release, only
support for 2 Infoforms are provided, a SysOp Infoformation one, and a NUV
Infoform which is used in conjunction with the New User Voting Booth. Due to
the "module" nature of this PPE, it will be possible for future enhancements
to allow more then 2 Infoforms, thou we question that any need for additional
"questionaires" that would not be better served making use PCB's Main Menu
Questionaires since we assume any additional infoforms ( questionaires ) would
normally be aimed at presently validated usesr on the sysops board. Infoforms
are mandatory of all new users ( users whos security level is 1 when entering
the PPE ). The following is a breakdown of the components used in the Infoforms
so you ( the sysop ) will be able to customize the PPE to your needs
Filename(s): INFOFORM.1, 1.CFG, INFOFORM.2, 2.CFG
Path: \DATA
This is the SysOp and NUV Infoforms, and their config files. INFOFORM.*
may be any standard ANSi file ( created with Thedraw or otherwise ). It must
meet the following to be usable.
1) The ANSi screen must not be more then 21 lines down on the screen. This is
due in part to a bug in the PPL language to preserve the SysOps screen
from scrolling ( since the sysop has the 2 line stat bar on the bottom of
the screen.
2) The ANSi screen should be saved in as few lines as possible in your editor
by using larger line lenghts. This assists SysOps/Users with incorrectly
set page lenghts.
3) NO ANIMATION ANSi's are permitted ( sorry )
After creating your ANSi Infoform, you will need to create a *.CFG file
for the PPE to work with in connection with your ANSi. The *.CFG file is
pretty simple, it is read by the PPE to position the cursor at each question
as the user fills it out. It ( the *.CFG file ) contains infoformation on the
X,Y position to place the answer, how long the answer may be, and the color
to make the answers inputed by the user. for example, a 1.CFG file may contain
the following it in.
2;5;35;@X01
3;5;40;@X01
The following lines above would instruct the PPE that only 2 questions are
contained in the infoform ( only 2 lines above :) ), and that the first
questions answer by the user should start at cursor position 2,5 and that the
answer may no exceed 35 characters, and it shall be in the PCB color od @X01
Question 2 is at cursor position 3,5 with a limit of 40 characters. Simple heh?
The Infoform.* and *.CFG files are also used by the NUV to correctly place the
users answers back into the correct position in the respected infoforms.
Filename(s): *.*
Path: \INFOFORM
This path contains standard text files used by the PPE to store the
users answers to all infoforms. A Unique CRC numbering System is assigned to
each user providing support for a possible 4 billion users, and to provide
security of the infoforms, since it wouldbe hard for a hacker to tell who is
who based on the filename
Filename(s): *.*
Path: \NUV
This path contains the NUV records. These are standard text files used
by the PPE to track a New Users voting record, and who voted on the new user.
Usage of this method allows for NON-MANDATORY voting on new users, unlike other
PPE's. This allows a validated user to vote later on a new user ( providing the
new user is still in the NUV ) instead of being FORCED to on the current logon.
Also contained in this file is a list of the users that voted, what those users
voted ( Yes or No ), the amount of voted, voting user comments and who left
them, the username CRC, and who casted the deciding vote.
Filename(s): TUNINFO.WEL
Path: \DISPLAY
This standard ANSi file is displayed to new users when entering the
INFOFORM part of the PPE before they start filling out same.
** Hints: On our nightly event batch file ( or may be a standalone batchfile,
we added the following lines.
del usercrc.lst
del usercrc.nuv
for %%x in (drive:\path\tunlogon\infoform\*.*) do type %%x >> usercrc.lst
for %%x in (drive:\path\tunlogon\nuv\*.*) do type %%x >> usercrc.nuv
This takes ALL the infoforms and NUV records, and places them into 2 large
files containing ALL the records. Sometimes you will find this useful to
quickly look up a user or review the NUV records, or to find out a users CRC #
*** Known bugs: As will ALL INFOFORM/NUV PPE's, if a user drops carrier in the
middle of completing any of the infoforms, he/she will NOT be entered into the
NUV. The result is a "lost" user with a security level of 1 in your database.
Presently, we look at whos in the newuser index to see who IS in the NUV, and
then delete any other level 1 users from the userbase using PCBSM. We believe
we have found a reliable way to fix this, but it has NOT be incorporated into
this public beta release yet, as we are still "alpha" testing the idea.
Welcome Screen Randomizer
-----------------------------------
Filename(s): *.*
Path: \WELCOME
The welcome screens may be standard text or ANSi files. PCB Macro codes
are valid as well. You may have as many welcome screens as you can fit into
the \WELCOME directory that your hard drive space permits. Filenames are NOT
important, since the PPE will auto detect all the files in there, and choose
one at random. This is presented to the user BEFORE the turbo-logon prompt.
Last Callers Options
---------------------
The last callers module provided with this PPE uses the SysOp Comment
Number one instead of the users LOCATION in its display. A future enhancement
module will allow those SysOps of PD/Shareware boards use the LOCATION.
In the TUNLGON.CFG file, you will find setting to customize the colors used
in this display file, as well as the total amount of last callers you wish to
track ( we recommend 16, but set it no less then 2, and the max. number is
unlimited to the best of our knowledge, but we suggest no more then 50 ).
Filename(s): LASTCALL.WEL
Path: \DISPLAY
This standard ANSi file is used as the display header shown on the top
of the last callers screen. Edit this as you need to reflect your boards name
or anyway you wish. We recommend limiting it to 3-4 lines MAx. for best display
results.
Filename(s): LASTCALL.ERS
Path: \DATA
This file contains the actually last callers to the board that is
displayed to the user. This is the file modified by the PPE per caller.
One-Liners
-----------
The TUNLogonPPE only supports @X PCB Color codes and does NOT offer pipe
color code commands. You may have as many 1 liners listed as you wish, this is
defineable in the TUNLGON.CFG file, but it must be more then 2, and we
recommend no more then 50.
Filename(s): TUN1LINE.WEL
Path: \DISPLAY
This ANSi file is used as a header on the 1 liners ( top of the screen )
Edit/create this file as warranted to meet the needs of your board.
Filename(s): TUN1LINE.DAT
Path: \DATA
This file actually contains the 1 liners left by users for display. Edit
this file to remove unwanted 1 liners as warranted.
Filename(s): TUN1LINE.PMT
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user if he
or she wishes to add a 1 liner to your logon process. Customize this file as
warranted for your boards needs and the look your desire. Standard PCB @X
Color Codes are valid as well.
Filename(s): TUN1LINE.AD1
Path: \DISPLAY
This standard ASCii/ANSi file is displayed to the user if he/she sez
YES to adding a 1 liner. Normally, you would reflect 1 liner guidelines and
instructions in this screen. Customize this file as warranted for your boards
needs and the look your desire. Standard PCB @X Color Codes are valid as well.
Filename(s): TUN1LINE.AD2
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user to
confirm if the 1 liner they just entered is correct, allowing them a chance
to review it and re-enter/abort as desired. Customize this file as warranted
for your boards needs and the look your desire. Standard PCB @X Color Codes
are valid as well.
Filename(s): TUN1LINE.AD3
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user to hit
any key to continue and telling him his little 1 liner has been added. It is
INDEPENDENT of the prompt.wel file used elsewhere to prompt the user to hit a
key to carry on. Customize this file as warranted for your boards needs and
the look your desire. Standard PCB @X Color Codes are valid as well.
The New User Voting
----------------------
New User Voting is one of the excellent features of this PPE. In
conjunction with the INFOFORM parts, this PPE provides you will everything you
need to have a full NUV. Defining of the level to vote, and default validated
user setting ( for users voted in ), and the number of yes/no votes are all
defineable in the TUNLGON.CFG file.
Filename(s): TUNNUV.WEL
Path: \DISPLAY
This ANSi screen is shown to users when entering the NUV in conjunction
with the prompts of total amount of new users for the user to vote on and if
he/she wishes to vote at this time.
Filename(s): TUNNUV.HDR
Path: \DISPLAY
This standard ANSi screen is used during the voting process. It is used
for displaying the new users name, vote count, etc. RIGHT NOW, the locations
that the PPE places the username, total votes, and votes needed are HARD CODED
so if you customize this screen, take that into effect. IN THE FUTURE, expect
a few lines in the TUNLGON.CFG file to allow you to place this information
where you want on the screen, but until then, sorry.
Filename(s): NUVMENU.WEL
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user for
input related to the NUV Menu Commands. It is shown after the .HDR file
listed above.Customize this file as warranted for your boards needs
and the look your desire. Standard PCB @X Color Codes are valid as well.
Filename(s): NUVCMNT.HDR
Path: \DISPLAY
This standard ASCii/ANSi file is used as the header on the top of the
screen that displays to the voting user other comments left from other users
that voted ahead of them. Customize this file as warranted for your boards
needs and the look your desire. Standard PCB @X Color Codes are valid as well.
Filename(s): TUNNUV.AD1
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user while
the NUV checks for any new users for the current user to vote on.
Customize this file as warranted for your boards needs and the look your
desire. Standard PCB @X Color Codes are valid as well.
Filename(s): TUNNUV.AD2
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user that no
new users exist for the current user to vote on.
Customize this file as warranted for your boards needs and the look your
desire. Standard PCB @X Color Codes are valid as well.
Filename(s): TUNNUV.AD3 and TUNNUV.AD4
Path: \DISPLAY
These 2 standard ASCii/ANSi files work together. It is used to tell the
user that there are new users available to vote on and how many. The files
are presented with the PPE placing the number of users inbetween.
for example,
TUNNUV.AD3 may look like this
There are a total of
and TUNNUV.AD4 may look like this
User(s) for you to vote on
The result to the user online would be
There are a total of 4 User(s) for you to vote on
As you see, the 2 files are used to create a total effect. Please note,
as with most of the prompts, the End Of File (EOF) should be RIGHT at the
end of the sentence, there should NOT be a blank ( or empty ) line under it
otherwise, it will split the above into 3 parts instead of 1 sentence.
Filename(s): TUNNUV.AD5
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user if
he/she wishes to vote on new users at this time ( if any of course )
Customize this file as warranted for your boards needs and the look your
desire. Standard PCB @X Color Codes are valid as well.
Filename(s): TUNNUV.AD6
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user that
he/she had voted YES to the current New User listed.
Customize this file as warranted for your boards needs and the look your
desire. Standard PCB @X Color Codes are valid as well.
Filename(s): TUNNUV.AD7
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user that
he/she had voted NO to the current New User listed.
Customize this file as warranted for your boards needs and the look your
desire. Standard PCB @X Color Codes are valid as well.
Filename(s): TUNNUV.AD8
Path: \DISPLAY
This standard ASCii/ANSi file is used as the prompt to the user to
ask if he/she wishes to leave a comment to other voting users.
Customize this file as warranted for your boards needs and the look your
desire. Standard PCB @X Color Codes are valid as well.
Filename(s): NEWUSERS.IDX
Path: \DATA
This standard text file MUST exist ( even if empty ). It contains a list
of new users that is currently in the NUV process. Editting it isnt actually
recommended, but can be done. The PPE pretty much maintains this file. Use
this file to compare against your userbase for "lost" new users ( Lost new
users are users that didnt complete the infoforms ( dropped carrier ), and
are marked as level 1, no delete in your userbase. ). Any user with a level of
1 and doesnt have the DELETE USER flag set in your userbase should be also
listed in the NEWUSERS.IDX file, if NOT, delete the user from YOUR USERBASE.
As noted in the infoforms, we believe we have found a way to defeat this bug
that is present on ALL INFOFORM.NUV PPE's but it has yet to be invoked in this
public beta release until we finish alpha testing it.
Suggested Uploads/SysOp Options
--------------------------------
(This section will focus on the suggested uploads screen or basic instructions
on how to setup external 3rd party PPE's to be called within the logon
process such as Top UL/DL, last message, or other popular PPE's )
Very Brief, you should be able to call 3rd party PPE's via the standard !
command in the TUNLTUSR.MSG file contained in \DATA. The header ( top of
screen ) is contained in TUNLTUSR.WEL in the \DISPLAY directory.
System News
------------
The System News uses standard TEXT files. The date of the file is
compared to the users last call data. Reading is mandatory and is NOT skipped
by the turbologon process.
Filename(s): *.*
Path: \NEWS
Place news files into this directory. Filenames are not important as
long as they are validate DOS filesname, and the total number is unlimited.
Filename(s): TUNNEWS.WEL
Path: \DISPLAY
Header displayed on the top of all news bulletins. Edit as warranted.
==============================================================================
------------------------------------------------------------------------------
REGISTRATION
---------------
This PPE is NOT freeware. You are welcome to use it and pass it along to
any/all your firends and boards you visit. To register this PPE, insure
future updates, and removal the unregistered announcement send check or money
order for $5 made to and addressed as listed below.
*Please make sure to include the following information in order to get your
serial number and activation code
-The EXACT SysOps name as entered in PCBSETUP and the EXACT name of the board
as entered in the PCBSETUP ( Note, Case Sensitive ! )
Make Checks Payable To: Eric Lapham
Address: TUNWarez Programming Team
C/O 104 Johns Neck Road
Shirley, N.Y. 11967
U.S.A.
-------------------------------------------------------------------------------